Automated low power mode based upon aspects associated with vehicle

ABSTRACT

An example system is provided for playing media content with a media playback device in a vehicle The example system can obtain vehicle movement data indicative of movement of the vehicle and sound data indicative of sound in the vehicle. The example system can also determine that the vehicle movement data and the sound data are at a given level, and switch the media playback device to a low power consumption mode.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. application Ser. No.16/796,491, filed on Feb. 20, 2020, entitled AUTOMATED LOW POWER MODEBASED UPON ASPECTS ASSOCIATED WITH VEHICLE, which is a continuation ofU.S. application Ser. No. 15/972,822, filed May 7, 2018, U.S. Pat. No.10,606,549, entitled AUTOMATED LOW POWER MODE BASED UPON ASPECTSASSOCIATED WITH VEHICLE, the disclosures of which are herebyincorporated by reference in their entireties. To the extentappropriate, a claim of priority is made to each of the above-disclosedapplications.

BACKGROUND

Many people enjoy consuming media content while travelling or duringother activities. For example, many drivers and passengers listen toaudio content, such as songs, albums, podcasts, audiobooks, and othertypes of audible content, in vehicles. Typical sources of such audiocontent in vehicles include radios and fixed media players, such asdevices that can play media content from CDs, USB drives, or SD cards.Media content from such typical sources is not flexible or personalizedfor the listeners in vehicles.

Alternatively, mobile devices, such as mobile phones or tablets runningaudio streaming applications, can offer a personalized and flexiblemusic-consuming experience using large catalogs of media contentavailable from a media content server. However, mobile devices are notwell suited for a vehicle environment for various reasons, such as legalrestrictions and sophisticated user interfaces that are not convenientfor use in a vehicle.

There exists a need for a media playback system that is easy to use andcontrol for media content playback while providing personalized userexperience of consuming media content in a vehicle.

SUMMARY

In general terms, the present disclosure relates to playing mediacontent with a media playback device in a vehicle. In one possibleconfiguration and by non-limiting example, vehicle movement and soundlevel within can be measured. Based on those aspects, the mode ofplayback of the media content can be modified. Various aspects aredescribed in this disclosure, which include, but are not limited to, thefollowing aspects.

One aspect is an example method for playing media content with a mediaplayback device in a vehicle (102), the method including: obtaining(810) vehicle movement data indicative of movement of the vehicle (102);obtaining (830) sound data indicative of sound in the vehicle (102);upon determining (820, 840, 850) that the vehicle movement data and thesound data are at a given level, switching the media playback device toa low power consumption mode.

Another aspect is an example system for playing media content with amedia playback device (110) in a vehicle (102), the system including: atleast one processor (148); and memory (150) encoding instructions that,when executed by the at least one processor, causes the at least oneprocessor to: obtain vehicle movement data indicative of movement of thevehicle (102); obtain sound data indicative of sound in the vehicle(102); determine that the vehicle movement data and the sound data areat a given level; and switch the media playback device to a low powerconsumption mode.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an example system for streaming media content forplayback.

FIG. 2 is a block diagram of an example embodiment of a personal mediastreaming appliance (PMSA) system.

FIG. 3 is a block diagram of an example embodiment of a media deliverysystem.

FIG. 4 is a block diagram of an example embodiment of a vehicle mediaplayback system.

FIG. 5 is a block diagram of an example embodiment of a mobile computingdevice.

FIG. 6 schematically illustrates an example embodiment of the PMSAsystem.

FIG. 7 is a block diagram of an exemplary embodiment of a power savingengine of the PMSA system of FIG. 2.

FIG. 8 illustrates an exemplary method for modifying a playback mode forthe PMSA system based upon aspects associated with the vehicle.

DETAILED DESCRIPTION

Various embodiments will be described in detail with reference to thedrawings, wherein like reference numerals represent like parts andassemblies throughout the several views.

People spend a significant amount of time travelling in vehicles. Manyof them find that time to be more enjoyable when they are listening tomusic, watching videos, or otherwise consuming media content. Mediacontent includes audio and video content. Examples of audio contentinclude songs, albums, playlists, radio stations, podcasts, audiobooks,and other audible media content items. Examples of video content includemovies, music videos, television programs, and other visible mediacontent items. In many cases, video content also includes audio content.As used herein, the term “vehicle” can be any machine that is operableto transport people or cargo. Vehicles can be motorized ornon-motorized. Vehicles can be for public or private transport. Examplesof vehicles include motor vehicles (e.g., cars, trucks, buses,motorcycles), rail vehicles (e.g., trains, trams), tracked vehicles,watercraft (e.g., ships, boats), aircraft, human-powered vehicles (e.g.,bicycles), wagons, and other transportation means. A user can drive avehicle or ride in as a passenger for travelling. As used herein, theterm “travel” and variants thereof refers to any activity in which auser is in transit between two locations.

Consuming media content in a vehicle presents many challenges. Ingeneral, a user in a moving vehicle may have limited attention availablefor interacting with a media playback device due to the need toconcentrate on travel related activities, such as driving andnavigation. Therefore, while a vehicle is moving, it can be difficultfor a user in the vehicle to interact with a media playback devicewithout disrupting the driving or navigation. Further, the userinterface of a media playback device can be overly complex, or mayrequire such fine motor skills that it can be difficult to use whiletraveling in a vehicle. Voice-based user interfaces also encountersignificant challenges to use in a vehicle environment. The passengerareas of a vehicle are often noisy due to engine noise, road noise, windand weather noises, passenger noises, and the sound of any media contentthat may be playing on a media playback system in the vehicle. Thisnoise hampers the ability of the voice-based user interface to interactwith a user. Moreover, accessing media content while travelling may bedifficult, expensive, or impossible depending on network availability orcapacity along the route of travel. Further, accessing and playing mediacontent can require significant amounts of electric power. Thus, use ofa mobile device for media content playback during travel may beundesirable because it will drain the battery. It can also bechallenging to connect a media playback device to a vehicle's built-inaudio system because of the requirement to connect to auxiliary cablesor undergo a complicated wireless pairing process. Embodiments disclosedherein address some or all of these challenges. It should be understood,however, that various aspects described herein are not limited to use ofa media playback device during travel.

On the other hands, many users desire a personalized media consumingexperience. For example, a user can access almost limitless catalogs ofmedia content through various free or fee-based media delivery services,such as media streaming services. Users can use mobile devices or othermedia playback devices to access large catalogs of media content. Due tosuch large collections of media content, it is desired to make itpossible to customize a selection of media content to match users'individual tastes and preferences so that users can consume theirfavorite media content while traveling in a vehicle.

Many vehicles include a built-in media playback device, such as a radioor a fixed media player, such as a player that can play media contentfrom a CD, USB driver, or SD cards. However, the media content that isdelivered using these built in vehicle media playback devices is greatlylimited and is not flexible or customizable to the user.

Alternatively, a mobile device, such as a smartphone or a tablet, can beused by a user to enjoy personalized and flexible music consumingexperience in a vehicle by running music streaming applications thereon.However, mobile devices are not well suited for use in a vehicleenvironment for various reasons. For example, mobile devices are notreadily accessible or controllable while driving or navigating. Further,connection between a mobile device and a vehicle audio system is ofteninconvenient and unreliable. Moreover, the music streaming applicationis not automatically ready to run and play media content, and the userneeds to pick up the mobile device and open the music streamingapplication and control a sophisticated user interface to play mediacontent. Additionally, many users have limited mobile data available viatheir mobile devices and are concerned about data usage while using themusic streaming application in the vehicle. Battery drainage and legalrestrictions on use while driving are further drawbacks to using mobiledevices for playing media content in the vehicle.

To address these challenges, the present disclosure provides aspecial-purpose personal appliance that can be used for streaming mediain a vehicle. The appliance is also referred to herein as the personalmedia streaming appliance (PMSA). In some embodiments, the appliance isspecially designed to be dedicated for media streaming purposes in avehicle, and there is no other general use. Some embodiments of theappliance can operate to communicate directly with a media contentserver and receive streamed media content from the server via a cellularnetwork. In these embodiments, other computing devices, such mobiledevices, are not involved in this direct communication between theappliance and the media content server. Mobile data cost can be includedin the subscription of the media streaming service or a purchase priceof the personal appliance. Therefore, the customer's possible concernabout mobile data usage can be eliminated. In other embodiments, theappliance can connect to another computing device, such as a mobiledevice, that provides a mobile hotspot to enable the appliance tocommunicate with the media content server rather than the appliancecommunicating with it directly. For example, a mobile device is used toassist in communication between the appliance and the media contentserver.

Further, the appliance can be associated with a user account of the userfor the media streaming service so that the user can enjoy personalizedmedia content.

In some embodiments, the appliance provides a simplified user interfaceso that a user can easily control playback of media content in a vehiclewhile maintaining his or her focus on other tasks such as driving ornavigating. For example, the appliance has a limited set of physicalcontrol elements that are intuitively controllable for playback of mediacontent with little (often only one) input from a user. Examples of suchphysical control elements include a rotatable knob and one or morephysically-depressible buttons.

Further, in some embodiments, the appliance is configured to be easilymounted to an interior structure of a vehicle, such as a dashboard, sothat the user can easily reach the appliance.

In some embodiments, the appliance also provides an output interfacethat can be easily connected to a vehicle audio system, such as via anauxiliary input port or Bluetooth. Therefore, the media content streamedto the appliance can then be transmitted from the appliance to thevehicle audio system for playback in the vehicle.

In some embodiments, the appliance can includes a voice interactionsystem designed for voice interaction with a user in the noisyenvironment of a vehicle. In some embodiments, the appliance includesmultiple microphones that reduce the effects of ambient noise in thepassenger area of the vehicle. In an example, the appliance includes atleast three microphones: two directed to the passenger area of thevehicle and another facing away from the passenger area of the vehicleto pick up vibrations and low frequency noise for cancellation. Theappliance also applies spectral noise cancellation to reduce non-voicefrequencies. In addition, omni-directional noise cancellation is appliedin some embodiments to reduce omni-directional sound (e.g., vehiclenoise). Directional noise is detected by determining a differencebetween audio input detected by the two microphones facing the passengerarea. The difference is preserved as directional audio input. Theappliance further cancels out audio that it is currently playing,allowing the appliance to detect voice commands even over loud music,for instance. In this manner, the appliance is arranged to provide animproved voice-based interface in a vehicle environment.

Embodiments described herein are directed to playing media content witha media playback device in a vehicle. In these examples, movement of thevehicle can be measured. Further, a sound level within the vehicle canbe measured. Based upon the movement of the vehicle and the sound levelwithin the vehicle, the playback mode of the PMSA system can bemodified. See FIGS. 7-8 for additional details.

As described herein, consuming media content may include one or more oflistening to audio content, watching video content, or consuming othertypes of media content. For ease of explanation, the embodimentsdescribed in this application are presented using specific examples. Forexample, audio content (and in particular music) is described as anexample of one form of media consumption. As another example, a vehicleis described as an example of an environment in which media content isconsumed. Further, traveling (and in particular driving) in a vehicle isdescribed as an example of an activity during which media content isconsumed. However, it should be understood that the same concepts aresimilarly applicable to other forms of media consumption and to otherenvironments or activities, and at least some embodiments include otherforms of media consumption and/or are configured for use in otherenvironments or during other activities.

FIG. 1 illustrates an example system 100 for streaming media content forplayback. The system 100 can be used in a vehicle 80. The vehicle 80includes a dashboard 82 or a head unit 84. The system 100 includes oneor more media playback devices 104 configured to play media content,such as a personal media streaming appliance (PMSA) system 110, a mediadelivery system 112, a vehicle media playback system 114, and a mobilecomputing device 118. The system 100 further includes a datacommunication network 116 and an in-vehicle wireless data communicationnetwork 122.

The PMSA system 110 operates to receive media content that is provided(e.g., streamed, transmitted, etc.) by a system external to the PMSAsystem 110, such as the media delivery system 112, and transmit themedia content to the vehicle media playback system 114 for playback. Insome embodiments, the PMSA system 110 is a portable device which can becarried into and used in the vehicle 80. The PMSA system 110 can bemounted to a structure of the vehicle 80, such as the dashboard 82 orthe head unit 84. In other embodiments, the PMSA system 110 can beconfigured to be built in a structure of the vehicle 80. An example ofthe PMSA system 110 is illustrated and described in more detail withreference to FIGS. 2 and 6.

The media delivery system 112 operates to provide media content to oneor more media playback devices 104 via the network 116. In theillustrated example, the media delivery system 112 provides mediacontent to the PMSA system 110 for playback of media content using thevehicle media playback system 114. An example of the media deliverysystem 112 is illustrated and described in further detail herein, suchas with reference to FIG. 3.

The vehicle media playback system 114 operates to receive media contentfrom the PMSA system 110 and generates a media output 124 to play themedia content in the vehicle 80. An example of the vehicle mediaplayback system 114 is illustrated and described in further detailherein, such as with reference to FIG. 4.

The network 116 is a data communication network that facilitates datacommunication between the PMSA system 110 and the media delivery system112. In some embodiments, the mobile computing device 118 can alsocommunicate with the media delivery system 112 across the network 116.The network 116 typically includes a set of computing devices andcommunication links between the computing devices. The computing devicesin the network 116 use the links to enable communication among thecomputing devices in the network. The network 116 can include one ormore routers, switches, mobile access points, bridges, hubs, intrusiondetection devices, storage devices, standalone server devices, bladeserver devices, sensors, desktop computers, firewall devices, laptopcomputers, handheld computers, mobile telephones, vehicular computingdevices, and other types of computing devices.

In various embodiments, the network 116 includes various types ofcommunication links. For example, the network 116 can include wiredand/or wireless links, including cellular, Bluetooth, ultra-wideband(UWB), 802.11, ZigBee, and other types of wireless links. Furthermore,in various embodiments, the network 116 is implemented at variousscales. For example, the network 116 can be implemented as one or morevehicle area networks, local area networks (LANs), metropolitan areanetworks, subnets, wide area networks (WAN) (such as the Internet), orcan be implemented at another scale. Further, in some embodiments, thenetwork 116 includes multiple networks, which may be of the same type orof multiple different types.

In some embodiments, the network 116 can also be used for datacommunication between other media playback devices 104 (e.g., the mobilecomputing device 118) and the media delivery system 112. Because thenetwork 116 is configured primarily for data communication betweencomputing devices in the vehicle 80 and computing devices outside thevehicle 80, the network 116 is also referred to herein as anout-of-vehicle network for out-of-vehicle data communication.

Unlike the network 116, the in-vehicle wireless data communication 122can be used for direct data communication between computing devices(e.g., the media playback devices 104) in the vehicle 80. In someembodiments, the in-vehicle wireless data communication 122 is used fordirect communication between the PMSA system 110 and the mobilecomputing device 118. In other embodiments, the mobile computing device118 can communicate with the PMSA system 110 in the data communicationnetwork 116. In some embodiments, the in-vehicle wireless datacommunication 122 can also be used for data communication between thePMSA system 110 and the vehicle media playback system 114.

Various types of wireless communication interfaces can be used for thein-vehicle wireless data communication 122. In some embodiments, thein-vehicle wireless data communication 122 includes Bluetooth®technology. In other embodiments, the in-vehicle wireless datacommunication 122 includes WiFi® technology. In yet other embodiments,other suitable wireless communication interfaces can be used for thein-vehicle wireless data communication 122, such as near fieldcommunication (NFC) and a ultrasonic data transmission.

In some embodiments, the mobile computing device 118 is configured toplay media content independently from the PMSA system 110. In someembodiments, the mobile computing device 118 is a standalone computingdevice that, without the PMSA system 110 involved, can communicate withthe media delivery system 112 and receive media content from the mediadelivery system 112 for playback in the vehicle 80. An example of themobile computing device 118 is illustrated and described in furtherdetail herein, such as with reference to FIG. 5.

FIG. 2 is a block diagram of an example embodiment of the PMSA system110 of the media streaming system 100 shown in FIG. 1. In this example,the PMSA system 110 includes a user input device 130, a display device132, a wireless data communication device 134, a movement detectiondevice 136, a location determining device 138, a media content outputdevice 140, an in-vehicle wireless communication device 142, a powersupply 144, a power input device 146, a processing device 148, and amemory device 150.

In some embodiments, the PMSA system 110 is a system dedicated forstreaming personalized media content in a vehicle environment. At leastsome embodiments of the PMSA system 110 have limited functionalitiesspecifically selected for streaming media content from the mediadelivery system 112 at least via the network 116 and/or for providingother services associated with the media content streaming service. ThePMSA system 110 may have no other general use such as found in othercomputing devices, such as smartphones, tablets, and other smartdevices. For example, in some embodiments, when the PMSA system 110 ispowered up, the PMSA system 110 is configured to automatically activatea software application that is configured to perform the media contentstreaming and media playback operations of the PMSA system 110 using atleast one of the components, devices, and elements of the PMSA system110. In some embodiments, the software application of the PMSA system110 is configured to continue running until the PMSA system 110 ispowered off or powered down to a predetermined level. In someembodiments, the PMSA system 110 is configured to be free of any userinterface control that would allow a user to disable the automaticactivation of the software application on the PMSA system 110.

As described herein, the PMSA system 110 provides various structures,features, and functions that improve the user experience of consumingmedia content in a vehicle.

As illustrated, the PMSA system 110 can communicate with the mediadelivery system 112 to receive media content via the network 116 andenable the vehicle media playback system 114 to play the media contentin the vehicle. In some embodiments, the PMSA system 110 can communicatewith the mobile computing device 118 that is in data communication withthe media delivery system 112. As described herein, the mobile computingdevice 118 can communicate with the media delivery system 112 via thenetwork 116.

The user input device 130 operates to receive a user input 152 from auser U for controlling the PMSA system 110. As illustrated, the userinput 152 can include a manual input 154 and a voice input 156. In someembodiments, the user input device 130 includes a manual input device160 and a sound detection device 162.

The manual input device 160 operates to receive the manual input 154 forcontrolling playback of media content via the PMSA system 110. Inaddition, in some embodiments, the manual input 154 is received formanaging various pieces of information transmitted via the PMSA system110 and/or controlling other functions or aspects associated with thePMSA system 110.

In some embodiments, the manual input device 160 includes one or moremanual control elements configured to receive various manual controlactions, such as pressing actions and rotational actions. As describedherein, the physical input device 160 includes a manual control knob 510and one or more physical buttons 512, which is further illustrated anddescribed with reference to FIG. 6.

The sound detection device 162 operates to detect and record sounds fromproximate the PMSA system 110. For example, the sound detection device162 can detect sounds including the voice input 156. In someembodiments, the sound detection device 162 includes one or moreacoustic sensors configured to detect sounds proximate the PMSA system110. For example, acoustic sensors of the sound detection device 162includes one or more microphones. Various types of microphones can beused for the sound detection device 162 of the PMSA system 110.

In some embodiments, the voice input 156 is a user's voice (alsoreferred to herein as an utterance) for controlling playback of mediacontent via the PMSA system 110 In addition, the voice input 156 is auser's voice for managing various data transmitted via the PMSA system110 and/or controlling other functions or aspects associated with thePMSA system 110.

In some embodiments, the sound detection device 162 is configured tocancel noises from the received sounds so that a desired sound (e.g.,the voice input 156) is clearly identified. For example, the sounddetection device 162 can include one or more noise-canceling microphoneswhich are configured to filter ambient noise from the voice input 156.In addition or alternatively, a plurality of microphones of the sounddetection device 162 are arranged at different locations in a body ofthe PMSA system 110 and/or oriented in different directions with respectto the body of the PMSA system 110, so that ambient noise is effectivelycanceled from the voice input 156 or other desired sounds beingidentified.

In some embodiments, the sounds detected by the sound detection device162 can be processed by the sound processing engine 180 of the PMSAsystem 110 as described below.

Referring still to FIG. 2, the display device 132 operates to displayinformation to the user U. Examples of such information include mediacontent playback information, notifications, and other information.

In some embodiments, the display device 132 operates as a display screenonly and is not capable of receiving a user input. By receiving themanual input 154 only via the manual input device 160 and disablingreceipt of manual input via the display device 132, the user interfaceof the PMSA system 110 is simplified so that the user U can control thePMSA system 110 while maintaining focus on other activities in thevehicle 80. It is understood however that, in other embodiments, thedisplay device 132 is configured as a touch-sensitive display screenthat operates as both a display screen and a user input device. In yetother embodiments, the PMSA system 110 does not include a displaydevice.

As described herein, in some embodiments, the display device 132 isarranged at the manual input device 160. In other embodiments, thedisplay device 132 is arranged separate from the manual input device160.

The wireless data communication device 134 operates to enable the PMSAsystem 110 to communicate with one or more computing devices at a remotelocation that is outside the vehicle 80. In the illustrated example, thewireless data communication device 134 operates to connect the PMSAsystem 110 to one or more networks outside the vehicle 80, such as thenetwork 116. For example, the wireless data communication device 134 isconfigured to communicate with the media delivery system 112 and receivemedia content from the media delivery system 112 at least partially viathe network 116. The wireless data communication device 134 can be awireless network interface of various types which connects the PMSAsystem 110 to the network 116. Examples of the wireless datacommunication device 134 include wireless wide area network (WWAN)interfaces, which use mobile telecommunication cellular networktechnologies. Examples of cellular network technologies include LTE,WiMAX, UMTS, CDMA2000, GSM, cellular digital packet data (CDPD), andMobitex. In the some embodiments, the wireless data communication device134 is configured as a cellular network interface to facilitate datacommunication between the PMSA system 110 and the media delivery system112 over cellular network.

The movement detection device 136 can be used to detect movement of thePMSA system 110 and the vehicle 80. In some embodiments, the movementdetection device 136 is configured to monitor one or more factors thatare used to determine movement of the vehicle 80. The movement detectiondevice 136 can include one or more sensors that are configured to detectmovement, position, and/or orientation of the PMSA system 110. As anexample, the movement detection device 136 is operable to determine anorientation of the PMSA system 110. The movement detection device 136can detect changes in the determined orientation and interpret thosechanges as indicating movement of the PMSA system 110. In someembodiments, the movement detection device 136 includes anaccelerometer. In other embodiments, the movement detection device 136includes a gyroscope. Other sensors can also be used for the movementdetection device 136, such as a magnetometer, a GPS receiver, analtimeter, an odometer, a speedometer, a shock detector, a vibrationsensor, a proximity sensor, and an optical sensor (e.g., a light sensor,a camera, and an infrared sensor).

The location determining device 138 is a device that determines thelocation of the PMSA system 110. In some embodiments, the locationdetermining device 138 uses one or more of Global Positioning System(GPS) technology (which may receive GPS signals), Global NavigationSatellite System (GLONASS), cellular triangulation technology,network-based location identification technology, Wi-Fi positioningsystems technology, and combinations thereof.

The media content output device 140 is an interface that enables thePMSA system 110 to transmit media content to the vehicle media playbackdevice 114. Some embodiments of the PMSA system 110 do not have aspeaker and thus cannot play media content independently. In theseembodiments, the PMSA system 110 is not regarded as a standalone devicefor playing media content. Instead, the PMSA system 110 transmits mediacontent to another media playback device, such as the vehicle mediaplayback device 114 to enable the other media playback device to playthe media content, such as through the vehicle stereo system.

As illustrated, the PMSA system 110 (e.g., a media content processingengine 176 thereof in FIG. 2) can convert media content to a mediacontent signal 164, the media content output device 140 transmits themedia content signal 164 to the vehicle media playback system 114. Thevehicle media playback system 114 can play the media content based onthe media content signal 164. For example, the vehicle media playbacksystem 114 operates to convert the media content signal 164 into aformat that is readable by the vehicle media playback system 114 forplayback.

In some embodiments, the media content output device 140 includes anauxiliary (AUX) output interface 166 and a wireless output interface168.

The AUX output interface 166 is configured to connect the PMSA system110 to the vehicle media playback system 114 via a cable (e.g., a mediacontent output line 550 in FIG. 6) of the PMSA system 110. In someembodiments, as illustrated in FIG. 6, the media content output line 550extending from the PMSA system 110 is connected to an input connector340 (e.g., an auxiliary input jack or port) of the vehicle mediaplayback system 114. As illustrated herein, the media content outputline 550 can be of various types, such as an analog audio cable or a USBcable.

The wireless output interface 168 is configured to connect the PMSAsystem 110 to the vehicle media playback system 114 via a wirelesscommunication protocol. In some embodiments, the wireless outputinterface 168 is configured for Bluetooth connection. In otherembodiments, the wireless output interface 168 is configured for othertypes of wireless connection. In some embodiments, the wireless outputinterface 168 is incorporated into, or implemented with, the in-vehiclewireless communication device 142. For example, when the media contentoutput device 140 wirelessly transmits media content to the vehiclemedia playback system 114, the in-vehicle wireless communication device142 can be used to implement the wireless output interface 168 of themedia content output device 140.

Referring still to FIG. 2, the in-vehicle wireless communication device142 operates to establish a wireless data communication, such as thein-vehicle wireless data communication 122, between computing devices ina vehicle 80. In the illustrated example, the in-vehicle wirelesscommunication device 142 is used to enable the PMSA system 110 tocommunicate with other computing devices, such as the mobile computingdevice 118, in the vehicle 80. Various types of wireless communicationinterfaces can be used for the in-vehicle wireless communication device142, such as Bluetooth Technology®, WiFi® technology, a near fieldcommunication (NFC), and an ultrasound data transmission. The in-vehiclewireless communication is also referred to herein as a short-rangewireless communication.

The power supply 144 is included in the example PMSA system 110 and isconfigured to supply electric power to the PMSA system 110. In someembodiments, the power supply 144 includes at least one battery. Thepower supply 144 can be rechargeable. For example, the power supply 144can be recharged using the power input device 146 that is connected toan external power supply. In some embodiments, the power supply 144 isincluded inside the PMSA system 110 and is not removable from the PMSAsystem 110. In other embodiments, the power supply 144 is removable bythe user from the PMSA system 110.

The power input device 146 is configured to receive electric power tomaintain activation of components of the PMSA system 110. As describedherein, the power input device 146 is connected to a power source of thevehicle 80 (e.g., a vehicle power supply 540 in FIG. 6) and use theelectric power from the vehicle 80 as a primary power source to maintainactivation of the PMSA system 110 over an extended period of time, suchas longer than several minutes.

The processing device 148, in some embodiments, comprises one or morecentral processing units (CPU). In other embodiments, the processingdevice 148 additionally or alternatively includes one or more digitalsignal processors, field-programmable gate arrays, or other electroniccircuits.

The memory device 150 typically includes at least some form ofcomputer-readable media. Computer readable media includes any availablemedia that can be accessed by the PMSA system 110. By way of example,computer-readable media include computer readable storage media andcomputer readable communication media.

Computer readable storage media includes volatile and nonvolatile,removable and non-removable media implemented in any device configuredto store information such as computer readable instructions, datastructures, program modules, or other data. Computer readable storagemedia includes, but is not limited to, random access memory, read onlymemory, electrically erasable programmable read only memory, flashmemory and other memory technology, compact disc read only memory, blueray discs, digital versatile discs or other optical storage, magneticstorage devices, or any other medium that can be used to store thedesired information and that can be accessed by the PMSA system 110. Insome embodiments, computer readable storage media is non-transitorycomputer readable storage media.

Computer readable communication media typically embodies computerreadable instructions, data structures, program modules or other data ina modulated data signal such as a carrier wave or other transportmechanism and includes any information delivery media. The term“modulated data signal” refers to a signal that has one or more of itscharacteristics set or changed in such a manner as to encode informationin the signal. By way of example, computer readable communication mediaincludes wired media such as a wired network or direct-wired connection,and wireless media such as acoustic, radio frequency, infrared, andother wireless media. Combinations of any of the above are also includedwithin the scope of computer readable media.

The memory device 150 operates to store data and instructions. In someembodiments, the memory device 150 stores instructions for a mediacontent cache 172, a caching management engine 174, a media contentprocessing engine 176, a manual input processing engine 178, a soundprocessing engine 180, a voice interaction engine 182, and a powersaving engine 184.

Some embodiments of the memory device 150 include the media contentcache 172. The media content cache 172 stores media content items, suchas media content items that have been received from the media deliverysystem 112. The media content items stored in the media content cache172 may be stored in an encrypted or unencrypted format. In someembodiments, the media content cache 172 also stores metadata aboutmedia content items such as title, artist name, album name, length,genre, mood, era, etc. The media content cache 172 can further storeplayback information about the media content items and/or otherinformation associated with the media content items.

The caching management engine 174 is configured to receive and cachemedia content in the media content cache 172 and manage the mediacontent stored in the media content cache 172. In some embodiments, whenmedia content is streamed from the media delivery system 112, thecaching management engine 174 operates to cache at least a portion ofthe media content into the media content cache 172 so that at least aportion of the cached media content can be transmitted to the vehiclemedia playback system 114 for playback. In other embodiments, thecaching management engine 174 operates to cache at least a portion ofmedia content into the media content cache 172 while online so that thecached media content is retrieved for playback while the PMSA system 110is offline.

The media content processing engine 176 is configured to process themedia content that is received from the media delivery system 112, andgenerate the media content signal 164 usable for the vehicle mediaplayback system 114 to play the media content. The media content signal164 is transmitted to the vehicle media playback system 114 using themedia content output device 140, and then decoded so that the vehiclemedia playback system 114 plays the media content in the vehicle 80.

The manual input processing engine 178 operates to receive the manualinput 154 via the manual input device 160. In some embodiments, when themanual input device 160 is actuated (e.g., pressed or rotated) uponreceiving the manual input 154, the manual input device 160 generates anelectric signal representative of the manual input 154. The manual inputprocessing engine 178 can process the electric signal and determine theuser input (e.g., command or instruction) corresponding to the manualinput 154 to the PMSA system 110. In some embodiments, the manual inputprocessing engine 178 can perform a function requested by the manualinput 154, such as controlling playback of media content. The manualinput processing engine 178 can cause one or more other engines toperform the function associated with the manual input 154.

The sound processing engine 180 is configured to receive sound signalsobtained from the sound detection device 162 and process the soundsignals to identify different sources of the sounds received via thesound detection device 162. In some embodiments, the sound processingengine 180 operates to filter the user's voice input 156 from noisesincluded in the detected sounds. Various noise cancellationtechnologies, such as active noise control or cancelling technologies orpassive noise control or cancelling technologies, can be used for filterthe voice input from ambient noise. In examples, the sound processingengine 180 filters out omni-directional noise and preserves directionalnoise (e.g., an audio input difference between two microphones) in audioinput. In examples, the sound processing engine 180 removes frequenciesabove or below human speaking voice frequencies. In examples, the soundprocessing engine 180 subtracts audio output of the device from theaudio input to filter out the audio content being provided by thedevice. (e.g., to reduce the need of the user to shout over playingmusic). In examples, the sound processing engine 180 performs echocancellation. By using one or more of these techniques, the soundprocessing engine 180 provides sound processing customized for use in avehicle environment.

In other embodiments, the sound processing engine 180 operates toprocess the received sound signals to identify the sources of particularsounds of the sound signals, such as people's conversation in thevehicle, the vehicle engine sound, or other ambient sounds associatedwith the vehicle.

In some embodiments, a recording of sounds captured using the sounddetection device 162 can be analyzed using speech recognition technologyto identify words spoken by the user. The words may be recognized ascommands from the user that alter the playback of media content and/orother functions or aspect of the PMSA system 110. In some embodiments,the words and/or the recordings may also be analyzed using naturallanguage processing and/or intent recognition technology to determineappropriate actions to take based on the spoken words. Additionally oralternatively, the sound processing engine 180 may determine varioussound properties about the sounds proximate the PMSA system 110 such asvolume, dominant frequency or frequencies, etc. These sound propertiesmay be used to make inferences about the environment proximate to thePMSA system 110.

The voice interaction engine 182 operates to cooperate with the mediadelivery system 112 (e.g., a voice interaction server 204 thereof asillustrated in FIG. 3) to identify a command (e.g., a user intent) thatis conveyed by the voice input 156. In some embodiments, the voiceinteraction engine 182 transmits the user's voice input 156 that isdetected by the sound processing engine 180 to the media delivery system112 so that the media delivery system 112 operates to determine acommand intended by the voice input 156. In other embodiments, at leastsome of the determination process of the command can be performedlocally by the voice interaction engine 182.

In addition, some embodiments of the voice interaction engine 182 canoperate to cooperate with the media delivery system 112 (e.g., the voiceinteraction server 204 thereof) to provide a voice assistant thatperforms various voice-based interactions with the user, such as voicefeedbacks, voice notifications, voice recommendations, and othervoice-related interactions and services.

FIG. 3 is a block diagram of an example embodiment of the media deliverysystem 112 of FIG. 1. The media delivery system 112 includes a mediacontent server 200, a personal media streaming appliance (PMSA) server202, and a voice interaction server 204.

The media delivery system 112 comprises one or more computing devicesand provides media content to the PMSA system 110 and, in someembodiments, other media playback devices, such as the mobile computingdevice 118, as well. In addition, the media delivery system 112interacts with the PMSA system 110 to provide the PMSA system 110 withvarious functionalities.

In at least some embodiments, the media content server 200, the PMSAserver 202, and the voice interaction server 204 are provided byseparate computing devices. In other embodiments, the media contentserver 200, the PMSA server 202, and the voice interaction server 204are provided by the same computing device(s). Further, in someembodiments, at least one of the media content server 200, the PMSAserver 202, and the voice interaction server 204 is provided by multiplecomputing devices. For example, the media content server 200, the PMSAserver 202, and the voice interaction server 204 may be provided bymultiple redundant servers located in multiple geographic locations.

Although FIG. 3 shows a single media content server 200, a single PMSAserver 202, and a single voice interaction server 204, some embodimentsinclude multiple media servers, multiple PMSA servers, and/or multiplevoice interaction servers. In these embodiments, each of the multiplemedia servers, multiple PMSA serves, and multiple voice interactionservers may be identical or similar to the media content server 200, thePMSA server 202, and the voice interaction server, respectively, asdescribed herein, and may provide similar functionality with, forexample, greater capacity and redundancy and/or services from multiplegeographic locations. Alternatively, in these embodiments, some of themultiple media servers, the multiple PMSA servers, and/or the multiplevoice interaction servers may perform specialized functions to providespecialized services. Various combinations thereof are possible as well.

The media content server 200 transmits stream media 210 (FIG. 2) tomedia playback devices such as the PMSA system 110. In some embodiments,the media content server 200 includes a media server application 212, aprocessing device 214, a memory device 216, and a network access device218. The processing device 214 and the memory device 216 may be similarto the processing device 148 and the memory device 150, respectively,which have each been previously described. Therefore, the description ofthe processing device 214 and the memory device 216 are omitted forbrevity purposes.

The network access device 218 operates to communicate with othercomputing devices over one or more networks, such as the network 116.Examples of the network access device include one or more wired networkinterfaces and wireless network interfaces. Examples of such wirelessnetwork interfaces of the network access device 218 include wirelesswide area network (WWAN) interfaces (including cellular networks) andwireless local area network (WLANs) interfaces. In other examples, othertypes of wireless interfaces can be used for the network access device218.

In some embodiments, the media server application 212 is configured tostream media content, such as music or other audio, video, or othersuitable forms of media content. The media server application 212includes a media stream service 222, a media application interface 224,and a media data store 226. The media stream service 222 operates tobuffer media content, such as media content items 230A, 230B, and 230N(collectively 230), for streaming to one or more streams 232A, 232B, and232N (collectively 232).

The media application interface 224 can receive requests or othercommunication from media playback devices or other systems, such as thePMSA system 110, to retrieve media content items from the media contentserver 200. For example, in FIG. 2, the media application interface 224receives communication from the PMSA system 110, such as the cachingmanagement engine 174 thereof, to receive media content from the mediacontent server 200.

In some embodiments, the media data store 226 stores media content items234, media content metadata 236, media contexts 238, user accounts 240,and taste profiles 242. The media data store 226 may comprise one ormore databases and file systems. Other embodiments are possible as well.

As discussed herein, the media content items 234 (including the mediacontent items 230) may be audio, video, or any other type of mediacontent, which may be stored in any format for storing media content.

The media content metadata 236 provide various information associatedwith the media content items 234. In some embodiments, the media contentmetadata 236 includes one or more of title, artist name, album name,length, genre, mood, era, etc.

The media content metadata 236 operates to provide various pieces ofinformation associated with the media content items 234. In someembodiments, the media content metadata 236 includes one or more oftitle, artist name, album name, length, genre, mood, era, etc.

In some embodiments, the media content metadata 236 includes acousticmetadata, cultural metadata, and explicit metadata. The acousticmetadata may be derived from analysis of the track refers to a numericalor mathematical representation of the sound of a track. Acousticmetadata may include temporal information such as tempo, rhythm, beats,downbeats, tatums, patterns, sections, or other structures. Acousticmetadata may also include spectral information such as melody, pitch,harmony, timbre, chroma, loudness, vocalness, or other possiblefeatures. Acoustic metadata may take the form of one or more vectors,matrices, lists, tables, and other data structures. Acoustic metadatamay be derived from analysis of the music signal. One form of acousticmetadata, commonly termed an acoustic fingerprint, may uniquely identifya specific track. Other forms of acoustic metadata may be formed bycompressing the content of a track while retaining some or all of itsmusical characteristics.

The cultural metadata refers to text-based information describinglisteners' reactions to a track or song, such as styles, genres, moods,themes, similar artists and/or songs, rankings, etc. Cultural metadatamay be derived from expert opinion such as music reviews orclassification of music into genres. Cultural metadata may be derivedfrom listeners through websites, chatrooms, blogs, surveys, and thelike. Cultural metadata may include sales data, shared collections,lists of favorite songs, and any text information that may be used todescribe, rank, or interpret music. Cultural metadata may also begenerated by a community of listeners and automatically retrieved fromInternet sites, chat rooms, blogs, and the like. Cultural metadata maytake the form of one or more vectors, matrices, lists, tables, and otherdata structures. A form of cultural metadata particularly useful forcomparing music is a description vector. A description vector is amulti-dimensional vector associated with a track, album, or artist. Eachterm of the description vector indicates the probability that acorresponding word or phrase would be used to describe the associatedtrack, album or artist.

The explicit metadata refers to factual or explicit information relatingto music. Explicit metadata may include album and song titles, artistand composer names, other credits, album cover art, publisher name andproduct number, and other information. Explicit metadata is generallynot derived from the music itself or from the reactions or opinions oflisteners.

At least some of the metadata 236, such as explicit metadata (names,credits, product numbers, etc.) and cultural metadata (styles, genres,moods, themes, similar artists and/or songs, rankings, etc.), for alarge library of songs or tracks can be evaluated and provided by one ormore third party service providers. Acoustic and cultural metadata maytake the form of parameters, lists, matrices, vectors, and other datastructures. Acoustic and cultural metadata may be stored as XML files,for example, or any other appropriate file type. Explicit metadata mayinclude numerical, text, pictorial, and other information. Explicitmetadata may also be stored in an XML or other file. All or portions ofthe metadata may be stored in separate files associated with specifictracks. All or portions of the metadata, such as acoustic fingerprintsand/or description vectors, may be stored in a searchable datastructure, such as a k-D tree or other database format.

Referring still to FIG. 3, each of the media contexts 238 is used toidentify one or more media content items 234. In some embodiments, themedia contexts 238 are configured to group one or more media contentitems 234 and provide a particular context to the group of media contentitems 234. Some examples of the media contexts 238 include albums,artists, playlists, and individual media content items. By way ofexample, where a media context 238 is an album, the media context 238can represent that the media content items 234 identified by the mediacontext 238 are associated with that album.

As described above, the media contexts 238 can include playlists 239.The playlists 239 are used to identify one or more of the media contentitems 234. In some embodiments, the playlists 239 identify a group ofthe media content items 234 in a particular order. In other embodiments,the playlists 239 merely identify a group of the media content items 234without specifying a particular order. Some, but not necessarily all, ofthe media content items 234 included in a particular one of theplaylists 239 are associated with a common characteristic such as acommon genre, mood, or era.

In some embodiments, a user can listen to media content items in aplaylist 239 by selecting the playlist 239 via a media playback device104, such as the PMSA system 110. The media playback device 104 thenoperates to communicate with the media delivery system 112 so that themedia delivery system 112 retrieves the media content items identifiedby the playlist 239 and transmits data for the media content items tothe media playback device 104 for playback.

In some embodiments, the playlist 239 includes a playlist title and alist of content media item identifications. The playlist title is atitle of the playlist, which can be provided by a user using the mediaplayback device 104. The list of content media item identificationsincludes one or more media content item identifications (IDs) that referto respective media content items 170.

Each media content item is identified by a media content item ID andincludes various pieces of information, such as a media content itemtitle, artist identification (e.g., individual artist name or groupname, or multiple artist names or group names), and media content itemdata. In some embodiments, the media content item title and the artistID are part of the media content metadata 236, which can further includeother attributes of the media content item, such as album name, length,genre, mood, era, etc. as described herein.

At least some of the playlists 239 may include user-created playlists.For example, a user of a media streaming service provided using themedia delivery system 112 can create a playlist 239 and edit theplaylist 239 by adding, removing, and rearranging media content items inthe playlist 239. A playlist 239 can be created and/or edited by a groupof users together to make it a collaborative playlist. In someembodiments, user-created playlists can be available to a particularuser only, a group of users, or to the public based on a user-definableprivacy setting.

In some embodiments, when a playlist is created by a user or a group ofusers, the media delivery system 112 operates to generate a list ofmedia content items recommended for the particular user or theparticular group of users. In some embodiments, such recommended mediacontent items can be selected based at least on the taste profiles 242as described herein. Other information or factors can be used todetermine the recommended media content items. Examples of determiningrecommended media content items are described in U.S. patent applicationSer. No. 15/858,377, titled MEDIA CONTENT ITEM RECOMMENDATION SYSTEM,filed Dec. 29, 2017, the disclosure of which is hereby incorporated byreference in its entirety.

In addition or alternatively, at least some of the playlists 239 arecreated by a media streaming service provider. For example, suchprovider-created playlists can be automatically created by the mediadelivery system 112. In some embodiments, a provider-created playlistcan be customized to a particular user or a particular group of users.By way of example, a playlist for a particular user can be automaticallycreated by the media delivery system 112 based on the user's listeninghistory (e.g., the user's taste profile) and/or listening history ofother users with similar tastes. In other embodiments, aprovider-created playlist can be configured to be available for thepublic in general. Provider-created playlists can also be sharable withto other users.

The user accounts 240 are used to identify users of a media streamingservice provided by the media delivery system 112. In some embodiments,a user account 240 allows a user to authenticate to the media deliverysystem 112 and enable the user to access resources (e.g., media contentitems, playlists, etc.) provided by the media delivery system 112. Insome embodiments, the user can use different devices (e.g., the PMSAsystem 110 and the mobile computing device 118) to log into the useraccount and access data associated with the user account in the mediadelivery system 112. User authentication information, such as ausername, an email account information, a password, and othercredentials, can be used for the user to log into his or her useraccount.

The taste profiles 242 contain records indicating media content tastesof users. A taste profile can be associated with a user and used tomaintain an in-depth understanding of the music activity and preferenceof that user, enabling personalized recommendations, taste profiling anda wide range of social music applications. Libraries and wrappers can beaccessed to create taste profiles from a media library of the user,social website activity and other specialized databases to mine musicpreferences.

In some embodiments, each taste profile 242 is a representation ofmusical activities, such as user preferences and historical informationabout the users' consumption of media content, and can include a widerange of information such as artist plays, song plays, skips, dates oflisten by the user, songs per day, playlists, play counts,start/stop/skip data for portions of a song or album, contents ofcollections, user rankings, preferences, or other mentions received viaa client device, or other media plays, such as websites visited, booktitles, movies watched, playing activity during a movie or otherpresentations, ratings, or terms corresponding to the media, such as“comedy”, “sexy”, etc.

In addition, the taste profiles 242 can include other information. Forexample, the taste profiles 242 can include libraries and/or playlistsof media content items associated with the user. The taste profiles 242can also include information about the user's relationships with otherusers (e.g., associations between users that are stored by the mediadelivery system 112 or on a separate social media site).

The taste profiles 242 can be used for a number of purposes. One use oftaste profiles is for creating personalized playlists (e.g., personalplaylisting). An API call associated with personal playlisting can beused to return a playlist customized to a particular user. For example,the media content items listed in the created playlist are constrainedto the media content items in a taste profile associated with theparticular user. Another example use case is for event recommendation. Ataste profile can be created, for example, for a festival that containsall the artists in the festival. Music recommendations can beconstrained to artists in the taste profile. Yet another use case is forpersonalized recommendation, where the contents of a taste profile areused to represent an individual's taste. This API call uses a tasteprofile as a seed for obtaining recommendations or playlists of similarartists. Yet another example taste profile use case is referred to asbulk resolution. A bulk resolution API call is used to resolve tasteprofile items to pre-stored identifiers associated with a service, suchas a service that provides metadata about items associated with thetaste profile (e.g., song tempo for a large catalog of items). Yetanother example use case for taste profiles is referred to asuser-to-user recommendation. This API call is used to discover userswith similar tastes by comparing the similarity of taste profile item(s)associated with users.

A taste profile 242 can represent a single user or multiple users.Conversely, a single user or entity can have multiple taste profiles242. For example, one taste profile can be generated in connection witha user's media content play activity, whereas another separate tasteprofile can be generated for the same user based the user's selection ofmedia content items and/or artists for a playlist.

Referring still to FIG. 3, the PMSA server 202 operates to providevarious functionalities to the PMSA system 110. In some embodiments, thePMSA server 202 includes a personal media streaming appliance (PMSA)server application 250, a processing device 252, a memory device 254,and a network access device 256. The processing device 252, the memorydevice 254, and the network access device 256 may be similar to theprocessing device 214, the memory device 216, and the network accessdevice 218, respectively, which have each been previously described.

In some embodiments, the PMSA server application 250 operates tointeract with the PMSA system 110 and enable the PMSA system 110 toperform various functions, such as receiving a user manual input,displaying information, providing notifications, performing powermanagement, providing location-based services, and authenticating one ormore users for the PMSA system 110. The PMSA server application 250 caninteract with other servers, such as the media content server 200 andthe voice interaction server 204, to execute such functions.

Referring still to FIG. 3, the voice interaction server 204 operates toprovide various voice-related functionalities to the PMSA system 110. Insome embodiments, the voice interaction server 204 includes a voiceinteraction server application 270, a processing device 272, a memorydevice 274, and a network access device 276. The processing device 272,the memory device 274, and the network access device 276 may be similarto the processing device 214, the memory device 216, and the networkaccess device 218, respectively, which have each been previouslydescribed.

In some embodiments, the voice interaction server application 270operates to interact with the PMSA system 110 and enable the PMSA system110 to perform various voice-related functions, such as voice feedbackand voice notifications. In some embodiments, the voice interactionserver application 270 is configured to receive data (e.g.,speech-to-text (STT) data) representative of a voice input received viathe PMSA system 110 and process the data to determine a user command(e.g., a user request or instruction). In some embodiments, at least oneof the media content server 200, the PMSA server 202, and the voiceinteraction server 204 may be used to perform one or more functionscorresponding the determined user command.

FIG. 4 is a block diagram of an example embodiment of the vehicle mediaplayback system 114. In this example, the vehicle media playback system114 includes a vehicle head unit 302, an amplifier 304, and a speaker306.

The vehicle head unit 302 is configured to receive a user input andgenerate media content from various sources. In this example, thevehicle head unit 302 includes a receiver 310, a wireless communicationdevice 312, a wired input device 314, a processing device 316, a memorydevice 318, a user input assembly 320, a display device 322, and astored media interface assembly 324.

The receiver 310 operates to receive media content signals from variousexternal sources. The received signals can then be used to generatemedia output by the vehicle media playback system 264. Some embodimentsof the receiver 310 include one or more tuners for receiving radiosignals such as FM or AM radio signals. Other embodiments of thereceiver 310 include a receiver for receiving satellite radio signalsand/or a receiver for receiving internet radio signals.

The wireless communication device 312 operates to communicate with otherdevices using wireless data signals. The wireless communication device312 can include one or more of a Bluetooth transceiver and a Wi-Fitransceiver. The wireless data signal may comprise a media contentsignal such as an audio or video signal. In some embodiments, thewireless communication device 312 is used to enable the vehicle mediaplayback system 114 to wirelessly communicate with the PMSA system 110and receive the media content signal 164 (FIG. 2) from the PMSA system110 via an in-vehicle wireless network. The in-vehicle wireless networkbetween the PMSA system 110 and the vehicle media playback system 114can be configured similarly to the in-vehicle wireless datacommunication 122 (FIG. 2).

The wired input device 314 provides an interface configured to receive acable for providing media content and/or commands. The wired inputdevice 314 includes an input connector 340 configured to receive a plugextending from a media playback device for transmitting a signal formedia content. In some embodiments, the wired input device 314 caninclude an auxiliary input jack (AUX) for receiving a plug from a mediaplayback device that transmits analog audio signals. The wired inputdevice 314 can also include different or multiple input jacks forreceiving plugs from media playback devices that transmit other types ofanalog or digital signals (e.g., USB, HDMI, Composite Video, YPbPr,DVI). In some embodiments, the wired input device 314 is also used toreceive instructions from other devices.

In some embodiments, the wired input device 314 provides the inputconnector 340 (e.g., an AUX port) for receiving a connector 552extending from the PMSA system 110, as illustrated in FIG. 6. The mediacontent signal 164 is then transmitted from the PMSA system 110 to thevehicle media playback system 114 via the cable 550, the connector 552,and the input connector 340.

The processing device 316 operates to control various devices,components, and elements of the vehicle media playback system 114. Theprocessing device 316 can be configured similar to the processing device148 (FIG. 2) and, therefore, the description of the processing device316 is omitted for brevity purposes.

In some embodiments, the processing device 316 operates to process themedia content signal 164 received from the PMSA system 110 and convertthe signal 164 to a format readable by the vehicle media playback system114 for playback.

The memory device 318 is configured to store data and instructions thatare usable to control various devices, components, and elements of thevehicle media playback system 114. The memory device 318 can beconfigured similar to the memory device 150 (FIG. 2) and, therefore, thedescription of the memory device 318 is omitted for brevity purposes.

The user input assembly 320 includes one or more input devices forreceiving user input from users for controlling the vehicle mediaplayback system 114. In some embodiments, the user input assembly 320includes multiple knobs, buttons, and other types of input controls foradjusting volume, selecting sources and content, and adjusting variousoutput parameters. In some embodiments, the various input devices aredisposed on or near a front surface of the vehicle head unit 302. Thevarious input devices can also be disposed on the steering wheel of thevehicle or elsewhere. Additionally or alternatively, the user inputassembly 320 can include one or more touch sensitive surfaces, which canbe incorporated in the display device 322.

The display device 322 displays information. In some embodiments, thedisplay device 322 includes a liquid crystal display (LCD) panel fordisplaying textual information about content and/or settings of thevehicle media playback system 114. The display device 322 can alsoinclude other types of display panels such as a light emitting diode(LED) panel. In some embodiments, the display device 322 can alsodisplay image or video content.

The stored media interface assembly 324 reads media content stored on aphysical medium. In some embodiments, the stored media interfaceassembly 324 comprises one or more devices for reading media contentfrom a physical medium such as a compact disc or cassette tape.

The amplifier 304 operates to amplify a signal received from the vehiclehead unit 302 and transmits the amplified signal to the speaker 306. Inthis manner, the media output 124 can be played back at a greatervolume. The amplifier 304 may include a power source to power theamplification.

The speaker 306 operates to produce an audio output (e.g., the mediaoutput 124) based on an electronic signal. The speaker 306 can includeone or more vehicle embedded speakers 330 disposed at various locationswithin the vehicle 80. In some embodiments, separate signals arereceived for at least some of the speakers (e.g., to provide stereo orsurround sound).

In other embodiments, the speaker 306 can include one or more externalspeakers 332 which are arranged within the vehicle 80. Users may bringone or more external speakers 332 into the vehicle 80 and connect theexternal speakers 332 to the vehicle head unit 302 using a wiredinterface or a wireless interface. In some embodiments, the externalspeakers 332 can be connected to the vehicle head unit 302 usingBluetooth. Other wireless protocols can be used to connect the externalspeakers 332 to the vehicle head unit 302. In other embodiments, a wiredconnection (e.g., a cable) can be used to connect the external speakers332 to the vehicle head unit 302. Examples of the wired connectioninclude an analog or digital audio cable connection and a universalserial bus (USB) cable connection. The external speaker 332 can alsoinclude a mechanical apparatus for attachment to a structure of thevehicle.

FIG. 5 is a block diagram of an example embodiment of the mobilecomputing device 118 of FIG. 1.

Similar to the PMSA system 110, the mobile computing device 118 can alsobe used to play media content. For example, the mobile computing device118 is configured to play media content that is provided (e.g., streamedor transmitted) by a system external to the mobile computing device 118,such as the media delivery system 112, another system, or a peer device.In other examples, the mobile computing device 118 operates to playmedia content stored locally on the mobile computing device 118. In yetother examples, the mobile computing device 118 operates to play mediacontent that is stored locally as well as media content provided byother systems.

In some embodiments, the mobile computing device 118 is a handheld orportable entertainment device, smartphone, tablet, watch, wearabledevice, or any other type of computing device capable of playing mediacontent. In other embodiments, the mobile computing device 118 is alaptop computer, desktop computer, television, gaming console, set-topbox, network appliance, blue-ray or DVD player, media player, stereo, orradio.

As described herein, the mobile computing device 118 is distinguishedfrom the PMSA system 110 in various aspects. For example, unlike thePMSA system 110, the mobile computing device 118 is not limited toplaying media content, but configured for a wide range offunctionalities in various situations and places. The mobile computingdevice 118 is capable of running a plurality of different softwareapplications for different purposes. The mobile computing device 118enables the user to freely start or stop activation of such individualsoftware applications.

In at least some embodiments, the mobile computing device 118 includes alocation-determining device 402, a display screen 404, a processingdevice 406, a memory device 408, a content output device 410, and anetwork access device 412. Other embodiments may include additional,different, or fewer components. For example, some embodiments mayinclude a recording device such as a microphone or camera that operatesto record audio or video content.

The location-determining device 402 is a device that determines thelocation of the mobile computing device 118. In some embodiments, thelocation-determining device 402 uses one or more of Global PositioningSystem (GPS) technology (which may receive GPS signals), GlobalNavigation Satellite System (GLONASS), cellular triangulationtechnology, network-based location identification technology, Wi-Fipositioning systems technology, and combinations thereof.

The display screen 404 is configured to display information. Inaddition, the display screen 404 is configured as a touch sensitivedisplay and includes a user interface 420 for receiving a user inputfrom a selector (e.g., a finger, stylus etc.) controlled by the user U.In some embodiments, therefore, the display screen 404 operates as botha display device and a user input device. The touch sensitive displayscreen 404 operates to detect inputs based on one or both of touches andnear-touches. In some embodiments, the display screen 404 displays agraphical user interface for interacting with the mobile computingdevice 118. Other embodiments of the display screen 404 do not include atouch sensitive display screen. Some embodiments include a displaydevice and one or more separate user interface devices. Further, someembodiments do not include a display device.

In some embodiments, the processing device 406 comprises one or morecentral processing units (CPU). In other embodiments, the processingdevice 406 additionally or alternatively includes one or more digitalsignal processors, field-programmable gate arrays, or other electroniccircuits.

The memory device 408 operates to store data and instructions. In someembodiments, the memory device 408 stores instructions for a mediaplayback engine 430.

The memory device 408 may be configured similarly to the memory device150 (FIG. 2) and, therefore, the description of the memory device 408 isomitted for brevity purposes.

The media playback engine 430 operates to play media content to the userU. As described herein, the media playback engine 430 is configured tocommunicate with the media delivery system 112 to receive one or moremedia content items (e.g., through the stream media 232). In otherembodiments, the media playback engine 430 is configured to play mediacontent that is locally stored in the mobile computing device 118.

In some embodiments, the media playback engine 430 operates to retrieveone or more media content items that are either locally stored in themobile computing device 118 or remotely stored in the media deliverysystem 114. In some embodiments, the media playback engine 430 isconfigured to send a request to the media delivery system 114 for mediacontent items and receive information about such media content items forplayback.

Referring still to FIG. 5, the content output device 410 operates tooutput media content. In some embodiments, the content output device 410generates media output 450 for the user U. In some embodiments, thecontent output device 410 includes one or more embedded speakers 452which are incorporated in the mobile computing device 118. Therefore,the mobile computing device 118 can be used as a standalone device thatgenerates the media output 450.

In addition, some embodiments of the mobile computing device 118 includean external speaker interface 454 as an alternative output of mediacontent. The external speaker interface 454 is configured to connect themobile computing device 118 to another system having one or morespeakers, such as headphones, portal speaker assemblies, and the vehiclemedia playback system 114, so that the media output 450 is generated viathe speakers of the other system external to the mobile computing device118. Examples of the external speaker interface 454 include an audiooutput jack, a Bluetooth transmitter, a display panel, and a videooutput jack. Other embodiments are possible as well. For example, theexternal speaker interface 454 is configured to transmit a signalthrough the audio output jack or Bluetooth transmitter that can be usedto reproduce an audio signal by a connected or paired device such asheadphones or a speaker.

The network access device 412 operates to communicate with othercomputing devices over one or more networks, such as the network 116 andthe in-vehicle wireless data communication 122. Examples of the networkaccess device 412 include wired network interfaces and wireless networkinterfaces. Wireless network interfaces includes infrared, BLUETOOTH®wireless technology, 802.11a/b/g/n/ac, and cellular or other radiofrequency interfaces in at least some possible embodiments.

FIG. 6 schematically illustrates an example embodiment of the PMSAsystem 110 of FIG. 1. In this example, the PMSA system 110 includes apersonal media streaming appliance (PMSA) 500 and a docking device 502.

As described herein, the PMSA system 110 is sized to be relatively smallso that the PMSA system 110 can be easily mounted to a structure (e.g.,a dashboard or head unit) of the vehicle 80 where the user canconveniently manipulate the PMSA system 110. By way of example, the PMSAsystem 110 is configured to be smaller than a typical mobile computingdevice, such as a smartphone. Further, the PMSA 500 provides asimplified user interface for controlling playback of media content. Forexample, the PMSA 500 has a limited set of physical control elements,such as a single rotary knob and one or more physical buttons asdescribed below, so that the user can easily control the PMSA system 110in the vehicle 80 (FIG. 1).

The PMSA 500 is configured to include at least some of the devices ofthe PMSA system 110 as illustrated with reference to FIG. 2. In someembodiments, the PMSA 500 includes all of the devices of the PMSA system110 as illustrated in FIG. 2.

As illustrated also in FIG. 2, some embodiments of the PMSA 500 includesthe user input device 130 that includes the manual input device 160 andthe sound detection device 162. Some embodiments of the manual inputdevice 160 include a control knob 510 and one or more physical buttons512.

In some embodiments, the control knob 510 is configured to bemaneuverable in multiple ways. For example, the control knob 510provides a plurality of regions on a knob face 514 that areindependently depressible upon receiving a user's pressing actionagainst the knob face 514. In the illustrated example, the control knob510 has five regions 516 (e.g., up, down, left, right, and middle) thatare separately depressible. At least some of the regions 516 areconfigured to receive inputs of different user commands (e.g., requestsor instructions).

In other embodiments, the control knob 510 is configured to bemanipulated in different ways, such as tilting in multiple directions orsliding in multiple directions.

In addition, the control knob 510 is configured to be rotatable. Forexample, the user can hold the control knob 510 and rotate with respectto a body 520 of the PMSA 500. The control knob 510 can be rotatable inboth directions 522 (e.g., clockwise and counterclockwise). In otherembodiments, the control knob 510 is configured to rotate in only onedirection.

The control knob 510 is used to receive user inputs for controllingplayback of media content. In addition or alternatively, the controlknob 510 can be used to receive user inputs for other purposes orfunctions.

The physical buttons 512 are configured to be depressed upon receiving auser's pressing action against the physical buttons 512. In theillustrated example, the PMSA 500 has four physical buttons 512A-512D.In some embodiments, each of the physical buttons 512 is configured toreceive a single user command. In other embodiments, at least one of thephysical buttons 512 is configured to receive multiple user commands.

In some embodiments, the physical buttons 512 are used as buttons thatare preset to be associated with particular media content, therebyfacilitating playback of such media content. In these embodiments, thephysical buttons 512 are also referred to as preset buttons 512.

In addition, the PMSA 500 also includes the display screen 132. In someembodiments, the display screen 132 is arranged at the knob face 514 ofthe control knob 510. As described herein, in some embodiments, thedisplay screen 132 does not include a touch sensitive display screen,and is configured as a display device only. In other embodiments,however, the display screen 132 can be configured to be touch sensitiveand receive a user input through the display screen 132 as well.

Referring still to FIG. 6, the docking device 502 is configured to mountthe PMSA 500 to a structure of the vehicle 80. The docking device 502 isconfigured to removably mount the PMSA 500 thereto. The docking device502 is further configured to attach to a structure of the vehicle 80(FIG. 1) so that the PMSA 500 is positioned at the structure of thevehicle 80.

In some embodiments, an interface between the PMSA 500 and the dockingdevice 502 is configured to prevent the PMSA 500 from rotating relativeto the docking device 502 when the control knob 510 is manipulated by auser. For example, the docking device 502 has a portion (e.g., a frontportion of the docking device 502) configured to interlock acorresponding portion of the PMSA 500 (e.g., a rear portion of the PMSA500) when the PMSA 500 is mounted to the docking device 502 such thatthe portion of the docking device 502 and the corresponding portion ofthe PMSA 500 form the interface therebetween.

In addition or alternatively, the PMSA 500 and the docking device 502include magnetic materials at the interface therebetween so that thePMSA 500 and the docking device 502 are magnetically coupled to eachother.

In some embodiments, the docking device 502 includes one or moreelectrical contacts 530 that are electrically connected to correspondingelectrical contacts (not shown in FIG. 6) of the PMSA 500 when the PMSA500 is mounted to the docking device 502. Such electrical connectionbetween the PMSA 500 and the docking device 502 is provided for variousfunctions.

First, as described herein, the PMSA 500 does not include a batterysufficient for a prolonged use without an external power supply. In someembodiments, the PMSA 500 is primarily powered by a vehicle power supply540. In some embodiments, the docking device 502 has a power receivingline 544 for connection to the vehicle power supply 540. For example,the power receiving line 544 extends from the docking device 502 and hasa power connector 546 at a free end that is configured to mate with avehicle power outlet 542 (e.g., a 12V auxiliary power outlet) of thevehicle power supply 540. As such, the docking device 502 receiveselectric power from the vehicle power supply 540 via the power receivingline 544, and the electrical connection between the PMSA 500 and thedocking device 502 is configured to deliver electric power from thedocking device 502 to the PMSA 500.

Second, as described herein, the PMSA 500 does not have a speaker and isdesigned to transmit media content signals to the vehicle media playbacksystem 114 so that the media content is played through the vehicle mediaplayback system 114. In some embodiments, the docking device 502includes a media content output line 550 (also referred to herein as amedia content output cable) (e.g., an auxiliary (AUX) output) configuredto connect with the vehicle media playback input connector 340 (e.g., anauxiliary (AUX) port) of the vehicle media playback system 114. Thedocking device 502 is configured to receive media content signals fromthe PMSA 500 via the electrical connection between the PMSA 500 and thedocking device 502, and transmit the signals to the vehicle mediaplayback system 114 via the media content output line 550. In theillustrated embodiment, the power receiving line 544 and the mediacontent output line 550 are combined to be a single line extending fromthe docking device 502 until the power connector 546, and the mediacontent output line 550 further extends (or branches out) from the powerconnector 546 and terminates at a media output connector 552. The mediaoutput connector 552 is configured to connect to the vehicle mediaplayback input connector 340 of the vehicle media playback system 114.In other embodiments, the media content output line 550 and the powerreceiving line 544 extend separately from the docking device 502.

In other embodiments, one or more of the power receiving line 544 andthe media content output line 550 are directly connected to, and extendfrom, the PMSA 500 so that electric power is directly supplied to thePMSA 500 without the docking device 502 involved, and that the mediacontent is directly transmitted to the vehicle media playback system 114without passing through the docking device 502.

Third, the electrical connection between the PMSA 500 and the dockingdevice 502 can be used to detect connection between the PMSA 500 and thedocking device 502.

Referring now to FIGS. 7-8, when the PMSA system 110 is playing backmedia content, the PMSA system 110 can also monitor various aspects ofthe vehicle 80 to estimate whether or not the user U in the vehicle isactually listening to the media content. For example, the user U maypark and exit the vehicle 80 without turning off the PMSA system 110. Insuch cases, the PMSA system 110 continues playing the media content(i.e., streaming the media content to the vehicle media playback system114). This can have undesired consequences, such as wasting power andbandwidth and can also make it difficult for the user U to identify thelast place listened in the media content.

More specifically, many vehicles are configured to continuing supplyingpower via a vehicle power source (e.g., the 12V auxiliary power outlet)after the engines are turned off. Therefore, the PMSA system may depletethe car battery if it is left on after the car is turned off. Therefore,the PMSA system may have a power save mode (e.g., sleep mode or standbymode) if not used, so that the PMSA system can reduce power andbandwidth requirements when not used, while still being programmed tocontinue playback when the user turns on the PMSA system upon returningto the vehicle (e.g., causing the PMSA system to return to a normalpower consumption mode).

By monitoring the movement of the vehicle 80, the PMSA system 110 canestimate when the vehicle stops. When the vehicle is stopped orotherwise stationary, it may be desirable to change the mode of the PMSAsystem 110 to, for example, a power save mode. However, in someinstances, the user U may stop the vehicle but still remain in thevehicle. In those instances, it may be desirable to continue playback ofthe media content.

Therefore, in some embodiments, the PMSA system 110 can also estimate asound level within the vehicle 80. The sound level within the vehicle 80can be associated with ambient noise created by occupants within thevehicle or the vehicle itself. For example, such ambient noise couldinclude noises associated with the vehicle engine, voices, audio fromthe PMSA system itself (other than playback of the media content),radio, and/or other playback devices in the car. The PMSA system 110 canbe programmed to determine whether or not to enter the power saving modebased upon the movement of the vehicle and the sound level within thevehicle 80.

Referring now to FIG. 7, additional details of the power saving engine184 of the PMSA system 110 are provided. Generally, the power savingengine 184 is programmed to determine a power mode for the PMSA system110 using, for example, vehicle movement and sound level. Based upon themovement and sound level, the power saving engine 184 is programmed toautomatically change the mode of the PMSA system 110 to a lower powerconsumption or power saving mode for certain scenarios.

As illustrated, the power saving engine 184 includes a movementdetection application 702, an ambient sound level application 704, andan automatic power mode application 706.

The movement detection application 702 determines movement by thevehicle 80. Specifically, the movement detection application 702receives input from the movement detection device 136. As noted, themovement detection device 136 can, in one example, be an accelerometeror other sensor that is positioned in the vehicle 80 to determinemovement of the vehicle. For example, the movement detection device 136can be arranged as a component of the PMSA system 110.

In some examples, the movement detection application 702 applies themovement data from the movement detection device 136 to a threshold todetermine whether or not the vehicle 80 is moving. When the movementdata indicates that the movement of the vehicle 80 falls below such athreshold, the movement detection application 702 indicates that thevehicle is not moving (e.g., stationary). In alternatives, other typesof comparisons can be used, such as simply requiring movement dataindicating no movement (i.e., zero) to determine an unmoving orstationary vehicle.

In some embodiments, the movement detection application 702 alsoincludes a temporal aspect. For example, when driving, the vehiclenaturally comes to rest at stop signs, light signals, etc. Therefore, amomentary lack of movement may not necessarily indicate a point at whichthe mode of play should be altered. To address this scenario, themovement detection application 702 may be required to detect a lack ofmovement for a particular period of time (e.g., 30 seconds, one minutes,five minutes, and/or ten minutes) before reporting the lack of movementto the automatic power mode application 706, as described below.

The example ambient sound level application 704 receives input from thesound detection device 162. As noted, the sound detection device 162can, in one example, be one or more microphones positioned in thevehicle 80 to determine an ambient sound level in the vehicle. Forexample, the microphones can be arranged as a component of the PMSAsystem 110.

Sound data from the sound detection device 162 can be provided to thesound processing engine 180. In some examples, the sound data that isgenerated by the sound detection device 162 is filtered by the soundprocessing engine 180 so that the ambient sound level as determined bythe ambient sound level application 704 is a better measure of theambient sound within the vehicle 80. For instance, the sound processingengine 180 can filter out or otherwise remove sound associated with theplayback of the media content from the sound data.

In this example, the filtered sound data is compared by the sounddetection device 162 to a threshold. This threshold can be static ordynamic and represents an ambient noise level at or above which anassumption is made that the vehicle is occupied. In other words, whenthe filtered sound data exceeds the threshold, the sound detectiondevice 162 indicates that the ambient noise in the vehicle is sufficientto indicate that the vehicle is occupied.

As noted with the movement data, the sound data can be analyzed over aperiod of time to determine the ambient sound level in the vehicle. Thiscan be desirable, for example, when the ambient sound is based uponspeech that naturally ebbs and flows. By averaging the sound data over aperiod of time (e.g., 30 seconds, one minutes, five minutes, and/or tenminutes), a better picture of the ambient sound level within the vehiclecan be obtained.

The automatic power mode application 706 receives input from themovement detection application 702 and the ambient sound levelapplication 704. Based upon the movement and ambient sound level data,the automatic power mode application 706 determines a desired playbackmode for the PMSA system 110. For instance, as noted, the automaticpower mode application 706 can change the PMSA system 110 to a lowerpower consumption mode, such as a standby or sleep mode, when a lack ofmovement and sound is reported by the movement detection application 702and the ambient sound level application 704.

More specifically, an example method 800 for determining an appropriatepower mode for the PMSA system based upon movement of and sound levelwithin the vehicle is shown.

At operation 810 of the method 800, a determination is made regardingmovement of the vehicle. At operation 820, the movement is compared to athreshold to determine whether or not the movement of the vehicle isbelow a threshold. If not, control is passed back to operation 810. Ifmovement is below the threshold (e.g., the vehicle is parked orotherwise stationary for a specific period of time), control is insteadpassed to operation 830.

At operation 830, the ambient sound level in the vehicle is determined.This can include, for example, the sound in the vehicle after the soundsassociated with the playback of the media content have been filteredout. Next, at operation 840, a determination is made as to whether ornot the ambient sound level in the vehicle is below a threshold. If not,control is passed back to operation 810. If the ambient sound level isbelow the threshold (e.g., for a specific period of time), control isinstead passed to operation 850.

At operation 850, a lower power saving mode is initiated for the PMSAsystem 110. In some example, this can be a lower power state thatincludes one or more of pausing the playback of the media content andplacing the PMSA system 110 in a state that requires less power. Asnoted, this process can include saving the position of the media contentplayback (e.g., elapsed playback time) prior to pausing or stopping.

Where user data is used, it can be handled according to a defined userprivacy policy and can be used to the extent allowed by the user. Wherethe data of other users is used, it can be handled in an anonymizedmatter so the user does not learn of the details of other usersgenerally or specifically.

The various examples and teachings described above are provided by wayof illustration only and should not be construed to limit the scope ofthe present disclosure. Those skilled in the art will readily recognizevarious modifications and changes that may be made without following theexamples and applications illustrated and described herein, and withoutdeparting from the true spirit and scope of the present disclosure.

1-15. (canceled)
 16. A method for playing media content with a mediaplayback device in a vehicle, the vehicle having a vehicle head unitseparate from the media playback device, comprising: obtaining vehiclemovement data indicative of movement of the vehicle using the mediaplayback device; obtaining sound data indicative of sound in the vehicleusing the media playback device; and upon determining that the vehiclemovement data and the sound data are at a given level, switching themedia playback device to a sleep mode.
 17. The method of claim 16,wherein obtaining sound data comprises obtaining the sound data over aperiod of time.
 18. The method of claim 17, wherein determining that thesound data is at the given level comprises: averaging the sound dataobtained over the period of time; and determining whether the averagedsound data is at the given level.
 19. The method of claim 17, furthercomprising filtering the sound data to exclude a noise, whereindetermining that the sound data is at the given level comprises:averaging the filtered sound data obtained over the period of time; anddetermining whether the averaged filtered sound data is at the givenlevel.
 20. The method of claim 16, further comprising: filtering thesound data to exclude a noise; and determining that the filtered sounddata is at the given level.
 21. The method of claim 20, wherein thegiven level represents a noise level indicating the vehicle is notoccupied.
 22. A system for playing media content with a media playbackdevice in a vehicle, the vehicle having a vehicle head unit separatefrom the media playback device, the system comprising: at least oneprocessor; and memory encoding instructions that, when executed by theat least one processor, causes the at least one processor to: obtainvehicle movement data indicative of movement of the vehicle; obtainsound data indicative of sound in the vehicle; determine that thevehicle movement data and the sound data are at a given level; andswitch the media playback device to a sleep mode.
 23. The system ofclaim 22, further comprising a plurality of microphones operable togenerate the sound data.
 24. The system of claim 23, wherein theplurality of microphones comprises: two passenger microphones directedto a passenger area of the vehicle; and one ambient noise microphonedirected away from the passenger area, wherein the sound data comprisessound data generated by each of the plurality of microphones.
 25. Thesystem of claim 24, wherein the at least one processor is further causedto: filter the sound data to exclude a noise; and determine that thefiltered sound data is at the given level.
 26. The system of claim 25,wherein filtering the sound data to exclude the noise comprisesfiltering out omni-directional noise.
 27. The system of claim 25,wherein filtering the sound data to exclude the noise comprisesfiltering out sound data above a human speaking voice frequency andbelow the human speaking voice frequency.
 28. The system of claim 22,wherein obtaining the sound data comprises obtaining the sound data overa period of time.
 29. The system of claim 28, wherein the at least oneprocessor is further caused to filter the sound data to exclude a noise.30. The system of claim 29, wherein the at least one processor isfurther caused to: average the filtered sound data obtained over theperiod of time; and determine whether the averaged filtered sound datais at the given level.
 31. The system of claim 30, wherein the givenlevel represents a noise level indicating the vehicle is not occupied.32. A computer readable medium storing instructions that, when executedby a computer, cause the computer to: obtain vehicle movement dataindicative of movement of a vehicle, the vehicle having a vehicle headunit separate from a media playback device for playing media content;obtain sound data indicative of sound in the vehicle; determine that thevehicle movement data and the sound data are at a given level; andswitch the media playback device to a sleep mode.
 33. The computerreadable medium of claim 32, wherein obtaining sound data comprisesobtaining the sound data over a period of time.
 34. The computerreadable medium of claim 33, wherein determining that the sound data isat the given level comprises: averaging the sound data obtained over theperiod of time; and determining whether the averaged sound data is atthe given level.
 35. The computer readable medium of claim 34, whereinthe given level represents a noise level indicating the vehicle is notoccupied.